Triple
T29581094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuel |
E753584
|
entity |
| Predicate | facesEnvironment |
P167464
|
FINISHED |
| Object | harsh environment |
—
|
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: harsh environment | Statement: [Manuel, facesEnvironment, harsh environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesEnvironment Context triple: [Manuel, facesEnvironment, harsh environment]
-
A.
faceType
Indicates the specific shape or structural category of a face that an entity possesses or is characterized by.
-
B.
facehuggerFunction
Indicates a parasitic interaction where one entity attaches to another’s face to implant or initiate a harmful internal process.
-
C.
facesBuilding
Indicates that one building is oriented toward and directly faces another building.
-
D.
faceVisibility
Indicates that one entity’s face is visible to another entity or from a particular viewpoint.
-
E.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7a4460819092b22b56609cc7ed |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:07 p.m.