Triple
T18985864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Target 5.4 |
E464556
|
entity |
| Predicate | linkedIndicator |
P134030
|
FINISHED |
| Object | Indicator 5.4.1 |
—
|
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: Indicator 5.4.1 | Statement: [Target 5.4, linkedIndicator, Indicator 5.4.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedIndicator Context triple: [Target 5.4, linkedIndicator, Indicator 5.4.1]
-
A.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
-
B.
linkedPosition
Indicates that one position is associated or connected to another position in a defined way.
-
C.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
D.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
E.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
- F. None of above. chosen
Provenance (4 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d65f7f08819088f56e8e030851b1 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.