Triple
T4365239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Poge Lighthouse |
E98754
|
entity |
| Predicate | numberOfRelocations |
P55796
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Cape Poge Lighthouse, numberOfRelocations, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRelocations Context triple: [Cape Poge Lighthouse, numberOfRelocations, multiple]
-
A.
relocationMethod
Indicates the means or process by which something or someone is moved from one location to another.
-
B.
relocationAnnouncedBy
Indicates that the relocation of something (such as a person, organization, or asset) was publicly communicated or made known by a particular agent or source.
-
C.
relocationStart
Indicates the point in time or event at which a relocation process for an entity begins.
-
D.
relocationCompleted
Indicates that a previously initiated relocation process has been fully carried out and successfully finished.
-
E.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351fea3e88190807b99868982c491 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.