Triple
T36493458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington-class aircraft carrier |
E899113
|
entity |
| Predicate | servedInPeriod |
P97182
|
FINISHED |
| Object | interwar period |
—
|
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: interwar period | Statement: [Lexington-class aircraft carrier, servedInPeriod, interwar period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedInPeriod Context triple: [Lexington-class aircraft carrier, servedInPeriod, interwar period]
-
A.
servedByTimePeriod
Indicates that a service, event, or activity occurs or is provided during a specified time period.
-
B.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
C.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
D.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
E.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4:10 p.m.