Triple
T18933416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natalie Scatorccio |
E463173
|
entity |
| Predicate | conflictedAbout |
P47733
|
FINISHED |
| Object | wilderness events |
—
|
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: wilderness events | Statement: [Natalie Scatorccio, conflictedAbout, wilderness events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictedAbout Context triple: [Natalie Scatorccio, conflictedAbout, wilderness events]
-
A.
conflictedBetween
chosen
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
formedInConflict
Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e57e648190aa4d3b09e84d4d38 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.