Triple

T38632089
Position Surface form Disambiguated ID Type / Status
Subject Pueblo de Los Ángeles E937475 entity
Predicate presentRemnant P44035 FINISHED
Object El Pueblo de Los Ángeles Historical Monument NE NERFINISHED

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: El Pueblo de Los Ángeles Historical Monument | Statement: [Pueblo de Los Ángeles, presentRemnant, El Pueblo de Los Ángeles Historical Monument]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: presentRemnant
Context triple: [Pueblo de Los Ángeles, presentRemnant, El Pueblo de Los Ángeles Historical Monument]
  • A. remnants chosen
    Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
  • B. remnantDetected
    Indicates that a remaining trace or leftover of a prior entity, event, or process has been identified.
  • C. presentOn
    Indicates that one entity is physically located on the surface or within the bounds of another entity.
  • D. lastRemnantOf
    Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
  • E. remnantUsedBy
    Indicates that a remaining part or leftover of something is utilized or employed by another entity.
  • 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_69f76ed5ca3c81909288f61fbf37b359 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fdee770af48190aca2670db50f8b49 completed May 8, 2026, 2:08 p.m.
PD Predicate disambiguation batch_69fdecec98a08190a357d816dc2a6dbe completed May 8, 2026, 2:02 p.m.
Created at: May 3, 2026, 4:32 p.m.