Triple
T37556920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habitat II |
E933719
|
entity |
| Predicate | producedOutcome |
P91959
|
FINISHED |
| Object | global plan of action for human settlements |
—
|
NE NERFINISHED |
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: global plan of action for human settlements | Statement: [Habitat II, producedOutcome, global plan of action for human settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedOutcome Context triple: [Habitat II, producedOutcome, global plan of action for human settlements]
-
A.
productionOutcome
chosen
Indicates the result or consequence produced by a given production process, activity, or event.
-
B.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
C.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
D.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
producedSaint
Indicates that an entity (such as a place, group, or lineage) has given rise to or brought forth a particular saint.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.