Triple
T13538479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOP-G |
E323320
|
entity |
| Predicate | habitationCapability |
P73935
|
FINISHED |
| Object | supports small crews for limited durations |
—
|
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: supports small crews for limited durations | Statement: [LOP-G, habitationCapability, supports small crews for limited durations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitationCapability Context triple: [LOP-G, habitationCapability, supports small crews for limited durations]
-
A.
habitation
Indicates that one entity serves as the dwelling place, residence, or living environment for another entity.
-
B.
hasResidenceCapacityFor
chosen
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
C.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
D.
regionOfHabitation
Indicates the geographic area or environment in which an entity typically lives or resides.
-
E.
canResideIn
Indicates that an entity is capable of living, staying, or being located within a specified place or environment.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.