Triple
T38526209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Love You Wall |
E923234
|
entity |
| Predicate | hasNumberOfInscriptions |
P12862
|
FINISHED |
| Object | over 300 |
—
|
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: over 300 | Statement: [I Love You Wall, hasNumberOfInscriptions, over 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfInscriptions Context triple: [I Love You Wall, hasNumberOfInscriptions, over 300]
-
A.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
B.
numberOfInscriptions
chosen
Indicates the total count of inscriptions associated with a given entity or object.
-
C.
hasInscriptionsFoundAt
Indicates that inscriptions associated with an entity have been discovered at a specified location.
-
D.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
-
E.
hasTypeOfInscriptions
Indicates that an entity bears or is associated with a specific kind or category of inscriptions.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 3, 2026, 4:32 p.m.