Triple
T5622784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galileo |
E147646
|
entity |
| Predicate | fullOperationalCapabilityTarget |
P7152
|
FINISHED |
| Object | 2020s |
—
|
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: 2020s | Statement: [Galileo, fullOperationalCapabilityTarget, 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullOperationalCapabilityTarget Context triple: [Galileo, fullOperationalCapabilityTarget, 2020s]
-
A.
operationalCapability
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
-
B.
fullyOperationalBy
chosen
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
E.
hasOperationalGoal
Indicates that an entity is associated with a specific objective or target it aims to achieve through its operations or activities.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02214b4948190b71a9f59499092f6 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.