Triple
T7459873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Harbor waterfront development |
E176216
|
entity |
| Predicate | isMixedUse |
P33911
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Harbor waterfront development, isMixedUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMixedUse Context triple: [National Harbor waterfront development, isMixedUse, true]
-
A.
propertyTypeMix
chosen
Indicates that an entity involves or consists of a combination of different types of properties rather than a single uniform property type.
-
B.
hasUrbanRuralMix
Indicates that something exhibits a combination or blend of both urban and rural characteristics or components.
-
C.
hasMultipleBuildings
Indicates that an entity possesses, controls, or is associated with more than one distinct building.
-
D.
mixedAt
Indicates that one entity has been combined or blended together with another entity (or entities), typically to form a mixture at a specific time or place.
-
E.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d525708190b7838e07ac2fbe1f |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.