Triple
T59929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern mockingbird |
E1187
|
entity |
| Predicate | territoriality |
P647
|
FINISHED |
| Object | highly territorial |
—
|
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: highly territorial | Statement: [Northern mockingbird, territoriality, highly territorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoriality Context triple: [Northern mockingbird, territoriality, highly territorial]
-
A.
claimsTerritory
chosen
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
-
B.
territorialChange
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
-
C.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
D.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
E.
sphereOfInfluence
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
- 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_69a24a552ef88190a0df287d68c65cba |
completed | Feb. 28, 2026, 1:52 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24e9f40908190a2f4a2111469b733 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 1:55 a.m.