Triple
T6392549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA Ship Thomas Jefferson |
E143862
|
entity |
| Predicate | missionSupport |
P55967
|
FINISHED |
| Object | port and harbor approaches |
—
|
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: port and harbor approaches | Statement: [NOAA Ship Thomas Jefferson, missionSupport, port and harbor approaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSupport Context triple: [NOAA Ship Thomas Jefferson, missionSupport, port and harbor approaches]
-
A.
missionField
Indicates a relationship where an entity’s work, activity, or purpose is directed toward a particular area, domain, or target context as its mission focus.
-
B.
missionLed
Indicates that an entity served as the leader or commander of a particular mission.
-
C.
missionContribution
chosen
Indicates that an entity plays a role in supporting, advancing, or fulfilling the mission or overarching purpose of another entity or organization.
-
D.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
E.
coordinatesDefenseSupport
Indicates organizing and directing defensive assistance or protective actions among involved entities.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0687db4b881909dd84d5a947cc3e3 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.