Triple
T20738383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont de Neuilly (Paris Métro) |
E509771
|
entity |
| Predicate | isOnAutomationLevel |
P9537
|
FINISHED |
| Object | fully automated |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: fully automated | Statement: [Pont de Neuilly (Paris Métro), isOnAutomationLevel, fully automated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnAutomationLevel Context triple: [Pont de Neuilly (Paris Métro), isOnAutomationLevel, fully automated]
-
A.
canAutomate
Indicates that one entity has the capability to perform, control, or execute another entity’s process or task automatically without continuous human intervention.
-
B.
automationLevel
chosen
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
C.
automatedIn
Indicates that an action, process, or operation is performed automatically within or by a specified system, context, or environment.
-
D.
isRobotic
Indicates that an entity is robotic, meaning it is a robot or operates using robotic mechanisms or technology.
-
E.
hasOnboardRobot
Indicates that one entity (typically a vehicle, device, or platform) is equipped with or carries a robot on board.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20c36708190898b889b6989fc7d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:32 p.m.