Triple
T9515646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Yard |
E229517
|
entity |
| Predicate | hasResidentialFacilityFor |
P73935
|
FINISHED |
| Object | brigades of midshipmen |
—
|
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: brigades of midshipmen | Statement: [The Yard, hasResidentialFacilityFor, brigades of midshipmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialFacilityFor Context triple: [The Yard, hasResidentialFacilityFor, brigades of midshipmen]
-
A.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
B.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
hasResidenceCapacityFor
chosen
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
D.
isPermanentHomeOf
Indicates that a location serves as the long-term, primary residence for a particular entity.
-
E.
ownsFacilityOn
Indicates that one entity possesses ownership or control over a facility located on or associated with another entity (such as a site, property, or area).
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986d5af08190a001c5a5ff647d4d |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.