Triple
T38518088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chula Uni |
E922392
|
entity |
| Predicate | refersToOwnership |
P198749
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [Chula Uni, refersToOwnership, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToOwnership Context triple: [Chula Uni, refersToOwnership, public]
-
A.
targetOwnership
Indicates that one entity holds ownership or proprietary control over the target entity.
-
B.
ownershipBasedIn
Indicates that an entity’s ownership or controlling stake is primarily located, registered, or based in a particular place or jurisdiction.
-
C.
ownershipSince
Indicates the point in time from which an entity has continuously owned another entity.
-
D.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
E.
ownershipConfers
Indicates that possessing or owning something grants the owner certain rights, powers, or privileges over it.
- F. None of above. chosen
Provenance (4 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
| PDg | Predicate description generation | batch_69ff02141dbc8190b00bcea2aa734b3a |
completed | May 9, 2026, 9:44 a.m. |
Created at: May 3, 2026, 4:32 p.m.