Triple
T33734266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellicott Complex |
E864364
|
entity |
| Predicate | isDistinctiveFor |
P14118
|
FINISHED |
| Object | clustered high-rise towers |
—
|
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: clustered high-rise towers | Statement: [Ellicott Complex, isDistinctiveFor, clustered high-rise towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDistinctiveFor Context triple: [Ellicott Complex, isDistinctiveFor, clustered high-rise towers]
-
A.
isDistinctiveGivenNameOf
Indicates that a given name uniquely and distinctively identifies or characterizes a particular entity compared to others.
-
B.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
C.
distinguéDe
Indicates that one entity is distinguished from or set apart as different from another entity.
-
D.
distinguishingTrait
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
E.
isDistinguishedBy
chosen
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb2376208190868d3ffd8aebc794 |
completed | May 3, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.