Triple
T15363211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craftsman |
E367341
|
entity |
| Predicate | acquisitionClosingDate |
P2754
|
FINISHED |
| Object | March 2017 |
—
|
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: March 2017 | Statement: [Craftsman, acquisitionClosingDate, March 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionClosingDate Context triple: [Craftsman, acquisitionClosingDate, March 2017]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
C.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
D.
deFactoTransferDate
Indicates the date on which control or ownership is effectively transferred in practice, regardless of the formal or legal transfer date.
-
E.
acquisitionAgreementYear
Indicates the calendar year in which an acquisition agreement between entities was made or came into effect.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.