Triple
T4354714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boll Weevil Monument |
E98117
|
entity |
| Predicate | hasUndergone |
P6390
|
FINISHED |
| Object | restoration and relocation within Enterprise |
—
|
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: restoration and relocation within Enterprise | Statement: [Boll Weevil Monument, hasUndergone, restoration and relocation within Enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergone Context triple: [Boll Weevil Monument, hasUndergone, restoration and relocation within Enterprise]
-
A.
underwent
chosen
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
B.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
C.
hadProcedure
Indicates that a subject underwent or received a specific medical or clinical procedure.
-
D.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
-
E.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c3aa1c8190aacebb8e80e5f2f8 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.